Skip to content

feat(peer-progress): add peer progress page and Anonymized Peers#1191

Open
mudith-perera wants to merge 1 commit intodoubtfire-lms:developmentfrom
mudith-perera:Feature/Peer-Progress-Anonymization
Open

feat(peer-progress): add peer progress page and Anonymized Peers#1191
mudith-perera wants to merge 1 commit intodoubtfire-lms:developmentfrom
mudith-perera:Feature/Peer-Progress-Anonymization

Conversation

@mudith-perera
Copy link
Copy Markdown

Description

A new Peer Progress feature has been added to the project navigation flow in doubtfire-web. The work introduced a new project state reachable from the header task dropdown, a summary page with a sample peer progress indicator, and a second anonymized peer view for comparing individual peer progress without exposing student identities.

The implementation includes:

  • A new projects/peer-progress state and component to act as the main entry page.
  • A sample cohort summary UI with:
  • cohort average
  • current student sample progress
  • peers-ahead count
  • strongest sample progress
  • a sample progress bar

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

  • Tests run:

    • ./node_modules/.bin/tsc -p src/tsconfig.app.json --noEmit
      Result: passed before the last router-injection tweak.

    • npm run build:angular1
      Result: passed and regenerated the AngularJS hybrid assets, including the new peer-progress and anonymized-peer state/template artifacts.

  • What these verified:

    • tsc checked the new Angular components and PeerProgressService for TypeScript/type-level issues.
    • build:angular1 verified the CoffeeScript/UI-Router state files compile, templates are added to build/templates-app.js, and the hybrid AngularJS runtime artifacts are generated.

Testing Checklist:

  • Tested in latest Chrome
  • Tested in latest Safari
  • Tested in latest Firefox

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have requested a review from @macite and @jakerenzella on the Pull Request

Previews

Screenshot 2026-04-24 at 4 41 30 am Screenshot 2026-04-24 at 4 42 18 am Screenshot 2026-04-24 at 4 42 48 am

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant